SLS: Example of Customer Enhancements

This example illustrates how you can model a supplementary logistics service (SLS) with sub-items, whereby the sub-items do not involve the recipients (pre-packed goods) but a different aspect of the SLS.

For SLS, you can only use procedures for additionals with a particular follow-up action. The standard system contains the follow-up action 85 , for example, for the SLS pre-packing. To create a new SLS, you have to define an additional follow-up action. To do so, maintain a new entry in view V_TWT_ACTION via the general table processing function (transaction sm30 ).

You need the following details for this new entry:

  • Flag the new follow-up action as relevant for SLS.

  • Specify that sub-items are to be generated for the follow-up action.

  • If you want a specific item category for items with SLS to be determined when sales orders or deliveries are created, you have to enter the relevant item usage. From the vendor's point of view, the entry you define here affects the creation of sales orders or warehouse orders. From the point of view of the customer, the settings apply to the creation of inbound deliveries or rough goods receipts.

You can also enter function modules in this view that perform certain tasks during SLS processing. The system calls the function modules at the appropriate point in the process. The standard configuration of SAP Retail contains function modules for pre-packing.

To map a different SLS, you have to develop your own function modules and enter them in this view. The module interfaces must be the same as those contained in the standard configuration. The following function modules exist for doing this:

  • Function module sort

  • View: customer

  • Point called: collective purchase order generation

  • Customer-specific module: required

This module arranges the issue-document schedule lines that are to be combined in sub-items in line with the criteria you define.

  • In the standard module: W_VAS_CPO_PP_ORDERS_SORT

  • Function group for the standard module: WFR15

  • Function module group switch

  • View: customer

  • Point called: collective purchase order generation

  • Customer-specific module: required

This module is also involved with user-specific sort criteria for issue-document schedule lines and recognizes where a different group starts. A new sub-item is created for each group in the collective purchase order.

  • In the standard module: W_VAS_CPO_PP_ORDERS_GC

  • Function group for the standard module: WFR16

  • Function module total packages

  • View: vendor

  • Point called: delivery packing

  • Customer-specific module: optional

This module results in a message being generated informing the user during the packing process of what has to be packed. If you want to use the packing functions, one of the modules contained in the standard system or one of your own modules has to be entered here.

  • In the standard module: W_VAS_DELIVEREY_DISPLAY_MESSAGE

  • Function group for the standard module: WFR19

  • Function module check packages

  • View: vendor or customer

  • Point called: delivery packing or entry of an inbound delivery (shipping notification or rough goods receipt)

  • Customer-specific module: optional

The module checks if items are combined in shipping units in accordance with the rules specified. If you want to use the packing functions, one of the modules contained in the standard system or one of your own modules has to be entered here.

  • In the standard module: W_VAS_DELIVERYPACKING_CHECK_PP

  • Function group for the standard module: WFR20

  • Function module check goods movement

  • View: customer

  • Point called: goods receipt

  • Customer-specific module: optional

This module results in a message being generated informing the user of the SLS so that he or she can check if the rules specified are complied with.

  • In the standard module: W_VAS_GR_CHECK_MESSAGE

  • Function group for the standard module: WFR18